-
-
Notifications
You must be signed in to change notification settings - Fork 398
[breaking] Fix: lib list --fqbn
and lib examples --fqbn
do not show platform bundled lib when lib of same name is installed globally
#2113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[breaking] Fix: lib list --fqbn
and lib examples --fqbn
do not show platform bundled lib when lib of same name is installed globally
#2113
Conversation
687bde3
to
46f6395
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2113 +/- ##
==========================================
+ Coverage 34.95% 35.00% +0.05%
==========================================
Files 232 232
Lines 20570 20556 -14
==========================================
+ Hits 7190 7196 +6
+ Misses 12531 12513 -18
+ Partials 849 847 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
46f6395
to
63ee372
Compare
This patch also fixes #1656 |
lib list --fqbn
does not shown platform bundled lib when lib of same name installed globallylib list --fqbn
and lib examples --fqbn
do not show platform bundled lib when lib of same name is installed globally
63ee372
to
106ccc6
Compare
106ccc6
to
4c8e0f7
Compare
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
For details see #1566, and #1656
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Yes, a public function in golang API has been removed.
Other information
Fix #1566
Fix #1656